According to statistics, Requirements management is identified as a major source of error to failed IT-projects. Moreover communication is identified as a factor affecting the require-ments management and can lead to deficiencies in the requirements. The requirements analyst is responsible for managing the requirements from the different stakeholders, act as a com-munication accommodator and to translate abstract requirements expressed by users to more specific requirements that developers can implement. The purpose of this thesis is to study the role of the requirements analyst to investigate the problems that may arise in working with Requirements management.  To achieve the purpose we have performed a Requirements management process in which we ourselves took the role as the requirements analysts. The Requirements management process consisted of three phases: gather requirements, document requirements and validate require-ments.

Requirements management is an important part of the software development process. The success of a project may depend on how this is handled. Even though several research studies indicates that more attention should be paid on non-functional requirements, the primary focus in practical projects still regards identifying functional requirements. Especially the prioritization of the non-functional requirements has been proven to be of great importance for the success of a project.This report investigates basics in agile Requirements management involving opinions from experts from a software development company. This is done with help of existing literature and interviews with key actors involved in prioritization at the company.

The education sector can be seen as a cornerstone of today's society, an organization that is under constant change and evolve as society. The compulsory school system is of significant role in society that places high demands on its management. The following study investigates the requirements for documentation in primary school organization and operations, and how these requirements are perceived and affect the school's organization and activities of the study carried out at different levels of the organization so as to get an overall picture of its impact. In order to analyze and create understanding of the results, the study applies the theory of New Public Management and various reforms that can be linked to the increased documentation requirements and its influence in the public administration. Study results show that there is a mixed picture of the documentation impact on the school system. Shown are both positive and negative effects of the documentation requirements.

This paper is a degree project on the C-level, 15 points at University West, Department of Business and IT dept. Informatics. This study is about agile methodology and its impact on IT projects. Requirements management is a process within an IT project, where customer has certain requirements that must be met by an IT system. The difference between the traditional and agile development is in the Requirements management process and it can cause problems in a project.

This final year project is dedicated to investigate the problem domain of system maintenance management. The purpose is to find problems in the system maintenance management of today. Whether there is any problem that can be elicitated in the requirements engineering?s phase that could help to obtain more maintenance management friendly systems and if it is not possible to obtain more maintenance management friendly, what else can be done?It has been learned that there are many problems today in the problem domain and the most great ones are the system documentation, stress and a systemknowledge lack among developers, system managers and system users.The requirements that have been found for this problem is good documentation, and use of simple solutions in the creating of the system..

This paper is a degree project on the C-level, 15 points at University West, Department of Business and IT dept. Informatics. This study is about agile methodology and its impact on IT projects. Requirements management is a process within an IT project, where customer has certain requirements that must be met by an IT system. The difference between the traditional and agile development is in the Requirements management process and it can cause problems in a project.

There are regulations in sweden that require organizations to manage occupational,  health and safetey (OH&S) issues in a systematic way. The contents of the management system vary depending of the activity of the specific organisation. An accurate management system is crucial in order to assure that rules and regulations are fullfilled. The OHSAS 18001 standard covering OH&S management is intended to provide organizations with the elements of an efficient OH&S management system. The work with this thesis was done at Swemat AB in Härnösand wich is a mechanical industry. In the thesis, the requirements of the OHSAS standard are compared with the current management system.

The result from Requirements Engineering is a Requirements Specification. Characteristics of a good Requirements Specification are unambiguity, completeness, verifiability, consistency, modifiability, traceability, correctness and ranked for importance and/or stability.This work defines these quality attributes and answers the questions how to reach these attributes and the diffuculties which exist in this area.This work should be read to get an overwiew of the area Requirements Engineering and Requirements Specification..

Modern IT systems tend to become more and more complex, while the number of active systems in companies increases. Furthermore, the number of security-related incidents is at an all-time high. These new conditions impose new demands on organizations. For example, it is no longer possible to manually collect and examine the systems log messages.The purpose of this thesis has been to make a comprehensive study of solutions for automated collecting and managing of log messages, analyze the Swedish Armed Forces specification for solutions for central log collection and management, and evaluating exis- ting solutions. The work consisted primarily of literature studies and evaluations of two of the Swedish Armed Forces of selected products: NetIQ Security Manager and Splunk.

Prioritisation of software requirements is a critical part of the development of software. Whichrequirements and in which order they will be developed is one of the main tasks that requirementprioritisation supports.There are different ways that a requirement prioritisation can be used, for example alone or in agroup and with different methods.The purpose of this report is to map out how you can carry out a requirement prioritisation alonewith different types of prioritisation methods and how you solve the problems that can arise whenprioritisting requirements. This is done by documenting the use of three different types of methodsthat can be execute alone. The methods are "100-dollar test", "Ranking" and "Top-tenrequirements".To be able to prioritise requirements, you need to establish which requirements you shall prioritise.The paper retrieves this information by interviewing stakeholders in the system and analysing theresult of the interviews and the execution of the requirement prioritisation.Three problems arose during that work and I present solutions on these problems. The problemswere 1) equivalent requirements when using the "100-dollar test", 2) low differentiation gradebetween the prioritised requirements in the "100-dollar test" and 3) that the requirements that wereprioritised weren't classified before the prioritisation, which leads to inaccuracies in the resultingprioritisation.The solution to the problems that the paper presents is to increase the amount of distributable unitsin the "100-dollar test" to 1000 per requirement, suggestions of classes of the requirements andthe combination of the methods "100-dollar test" and "ranking" to bypass the equivalentrequirements.The report is written in Swedish.Nyckelord: GoTRIS, requirements retrieval, requirements analysis, Viktoria Swedish ICT,requirements prioritisation, requirements, 100-dollar test, ranking, top 10 requirements..

Requirements engineering is a widespread topic in the research field of informatics. However, there is little research regarding lack of requirements documentation and how it is perceived. The same applies for how requirements engineering in retrospect can be implemented. This is a debated issue on blogs and forums but it has not been reflected in the research area.Therefore, this study concerns research questions regarding how the developers, testers and requirements analyst experience the lack of requirements documentation and how requirements engineering in retrospect can be implemented.To answer these questions, data collection has been conducted through qualitative interviews with individuals affected by this problem in their everyday work.This study has provided an explanation of how the problem is perceived and what the consequences are, both direct and indirect. The impacts are divided into three categories and are presented as, emotional consequences, system implications and consequences regarding re source consumption.

Det problemområde som behandlas i arbetet är den del av systemutvecklarens arbete avsett att hantera förändringar i kravbilden under systemutvecklingens hela livscykel, kallat Requirements management (RM). Arbetet fokuseras på detaljer kring spårbarhet inom förändringshantering.För att lyckas i spårbarhetsarbetet gäller det för systemutvecklaren att se hur de olika krav som finns i kravbilden är relaterade till varandra och var kraven har sitt ursprung. Det skiljs inom spårbarhetsområdet mellan framåt- och bakåtriktad spårbarhet. Vardera spårbarhetsriktningen delas sedan in i två steg från kravursprung framåt via kravdokumentation till realisering då det gäller den framåtriktade och från realisering via kravdokumentation till kravursprung då det gäller den bakåtriktade.En studie har genomförts där litteraturens syn har jämförts med ett antal respondenters då det gäller att dels kartlägga vilka typer av spårbarhet som behövs inom systemutvecklingsprojekt och dels vilket stöd som behövs för att etablera och underhålla denna spårbarhet..

The Swedish government decided in 1996 that the governmental authorities are to implemementenvironmental management systems. Each year, the Swedish Environmental ProtectionAgency compiles the authorities? reports on their environmental management systems. Thecompilation shows that not more than 20 % of the authorities perform environmental audits.This study aims to investigate the authorities? view of internal environmental audits, the incentivesof performing them.

Requirements engineering is a widespread topic in the research field of informatics. However, there is little research regarding lack of requirements documentation and how it is perceived. The same applies for how requirements engineering in retrospect can be implemented. This is a debated issue on blogs and forums but it has not been reflected in the research area.Therefore, this study concerns research questions regarding how the developers, testers and requirements analyst experience the lack of requirements documentation and how requirements engineering in retrospect can be implemented.To answer these questions, data collection has been conducted through qualitative interviews with individuals affected by this problem in their everyday work.This study has provided an explanation of how the problem is perceived and what the consequences are, both direct and indirect. The impacts are divided into three categories and are presented as, emotional consequences, system implications and consequences regarding re source consumption.

Requirements engineering is a widespread topic in the research field of informatics. However, there is little research regarding lack of requirements documentation and how it is perceived. The same applies for how requirements engineering in retrospect can be implemented. This is a debated issue on blogs and forums but it has not been reflected in the research area.Therefore, this study concerns research questions regarding how the developers, testers and requirements analyst experience the lack of requirements documentation and how requirements engineering in retrospect can be implemented.To answer these questions, data collection has been conducted through qualitative interviews with individuals affected by this problem in their everyday work.This study has provided an explanation of how the problem is perceived and what the consequences are, both direct and indirect. The impacts are divided into three categories and are presented as, emotional consequences, system implications and consequences regarding re source consumption.